Skip to content

Conversation

Mr-KRAMA
Copy link

Description

Adds CLI usage clarification to prevent users from using deprecated shadcn-cli command

Problem

Users experiencing "SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON" when using npx shadcn-cli@latest add navigation-menu. This happens because the old shadcn-cli package is deprecated and may be fetching from incorrect endpoints.

Solution

  • Added CLI usage section to installation documentation
  • Clarified that npx shadcn@latest should be used instead of npx shadcn-cli@latest
  • Added deprecation notice for the old CLI package
  • Updated both v4 and www documentation

Changes

  • Added "CLI" section with correct usage examples
  • Added deprecation warning for old shadcn-cli package

Related Issue

Fixes #8050

Testing

  • Documentation clearly shows correct CLI usage
  • Deprecation notice helps users avoid the old package
  • Both documentation sites updated consistently

Copy link

vercel bot commented Sep 25, 2025

@Mr-KRAMA is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.

@felores
Copy link

felores commented Sep 26, 2025

that could be one reason for the error but theres still no https://www.shadcn.io/registry/registry.json so shadcn MCP server is unable to use the shadcn.io registry

@Mr-KRAMA
Copy link
Author

@felores You're absolutely right! I just added the missing registry.json file.

The MCP server was failing because https://www.shadcn.io/registry/registry.json didn't exist. Now it's included in this PR with all the component data.

Once this gets merged, the MCP server should work perfectly. Thanks for pointing that out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug]: json registry error for shadcn components

2 participants